Merged
Conversation
GurtejSohi
requested review from
aaron-steinfeld,
ravisingal and
tim-mwangi
as code owners
GurtejSohi
changed the title
ravisingal
approved these changes
Mar 20, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
Due to a security incident, all trivy releases from v0.27.0 to v0.69.1 were permanently deleted. Refer goharbor/harbor#22895 for more details.
The SHA pointed to this commit of trivy-action which uses 0.64.1 version of trivy which also got deleted. Due to this, the trivy vulnerability scanner step in build action is failing in hypertrace repos (e.g. https://github.com/hypertrace/config-service/actions/runs/23290175030/job/67723807940?pr=340).
Fix is to update the SHA to point to the latest commit which uses v0.69.3 of trivy.